fix(test): unpack charge_spin in test_pt2_dual_artifact_for_gnn#5523
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe PR updates test ChangesArtifact interface test synchronization
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #5523 +/- ##
==========================================
- Coverage 82.19% 82.19% -0.01%
==========================================
Files 891 891
Lines 101599 101599
Branches 4241 4242 +1
==========================================
- Hits 83507 83506 -1
Misses 16789 16789
- Partials 1303 1304 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
#5431 extended
_make_sample_inputsto return a 7th tensor (charge_spin) and updated the exported-artifact signatures accordingly, but missedtest_pt2_dual_artifact_for_gnn: the test is decorated withskipif(CI == "true")(AOTInductor compile too slow for CI), so the breakage was invisible to CI and only surfaces on a local full run —ValueError: too many values to unpack (expected 6).Fix: unpack the 7th value and pass
charge_spinto both the regular and with-comm artifacts (it sits betweenaparamand the comm tensors in the exported signature).Verified locally:
source/tests/pt_expt/model/test_export_with_comm.py— 4 passed.Known limitation: this test remains CI-skipped by design, so future signature changes can silently break it again; running it locally before release is the only guard.
Summary by CodeRabbit